Subject/body encoding has drifted over time, resulting in mixed raw/encoded values in activeforums_Content and inconsistent rendering/email behavior. This PR standardizes persistence to store unencoded content and aligns rendering/token paths to avoid double-decoding.

• Storage normalization (single boundary)

  • Added Utilities.NormalizeHtmlForStorage(...) to decode HTML entities once before persistence.
  • Applied normalization in topic/reply save paths (SqlDataProvider.Topics_Save, SqlDataProvider.Reply_Save, and post submit flow in af_post.ascx.cs), including topic summary.

• Rendering/token alignment

  • Removed redundant HtmlDecode(...) in key read/render/edit mappings where data should now already be normalized:
    • TopicView / TopicsView content hydration
    • Post edit/reply form prefill in af_post.ascx.cs
    • TokenReplacer.ReplaceBody(...) decode path
  • Preserves existing output encoding behavior at render boundaries while preventing decode loops.

• Upgrade data conversion

  • Added sql/09.07.00-1607.SqlDataProvider to normalize existing activeforums_Content.Subject and Body values (including doubly encoded legacy patterns).
  • Registered the script in DnnCommunityForums.dnn.
  • Included in-script reference notes for latest relevant stored proc versions (activeforums_Topics_Save, activeforums_Reply_Save, activeforums_Topics_SaveToForum).

• Utility coverage

  • Added focused tests for Utilities.NormalizeHtmlForStorage(...) in UtilitiesTests (single decode behavior, empty/null handling).

internal static string NormalizeHtmlForStorage(string text)
{
    return string.IsNullOrEmpty(text) ? string.Empty : WebUtility.HtmlDecode(text);
}